Hello @Ole2mail, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

@Ole2mail thanks for your contribution. Note that anonymous contributions are not allowed, you need to sign off your commits with your real name. Thanks!

@Ole2mail thanks for signing the commit. You still have some CI issues though, please take a look.

@Ole2mail thanks for signing the commit. You still have some CI issues though, please take a look.

looking into this now

@Ole2mail thanks for signing the commit. You still have some CI issues though, please take a look.

seems like CI is not starting automatically, which makes uncertain what else is missing to fix for the CR/MR/PR.

don't see any fixable error on CI test. seems like the one has been "cancelled". what next to do?

if something has left unresolved yet?

btw @Ole2mail please don't mark conversation as resolved and let reviewers come back to their suggestions without losing track of changes they have asked for :) https://docs.zephyrproject.org/latest/contribute/contributor_expectations.html#workflow-suggestions-that-help-reviewers
Thanks!

seems like twister run has failed because of
#89826

can be fixed temporarily by adding to the file
tests/drivers/flash/common/testcase.yaml
following lines:

   drivers.flash.common.disable_spi_nor:                                                              
     platform_exclude:                                                                                
       - mikroe_quail   

would you like me to push a separate CR/MR/PR disabling faulty test?

@Ole2mail adding this file to the test should do the trick

diff --git a/tests/drivers/flash/common/boards/mikroe_quail.overlay b/tests/drivers/flash/common/boards/mikroe_quail.overlay
new file mode 100644
index 00000000000..88e8957e5d5
--- /dev/null
+++ b/tests/drivers/flash/common/boards/mikroe_quail.overlay
@@ -0,0 +1,18 @@
+/*
+ * Copyright (c) 2025 STMicroelectronics
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+&flash0 {
+	partitions {
+		compatible = "fixed-partitions";
+		#address-cells = <1>;
+		#size-cells = <1>;
+
+		/* Set last blocks of the code flash as storage partition */
+		storage_partition: partition@1e0000 {
+			label = "storage";
+			reg = <0x1e000 DT_SIZE_K(8)>;
+		};
+	};
+};

if something has left unresolved yet?

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Hi @Ole2mail!
Congratulations on getting your very first Zephyr pull request merged 🎉🥳. This is a fantastic achievement, and we're thrilled to have you as part of our community!

To celebrate this milestone and showcase your contribution, we'd love to award you the Zephyr Technical Contributor badge. If you're interested, please claim your badge by filling out this form: Claim Your Zephyr Badge.

Thank you for your valuable input, and we look forward to seeing more of your contributions in the future! 🪁